Internet protocol analyzing

ABSTRACT

Included are methods for facilitating routing of control data associated with a communication to a plurality of recorders. One such method, among others, includes receiving control data related to a communication and routing the received control data to at least one recorder via a layer  3  protocol.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. patent application Ser. No. 11/394,411, filed on Mar. 31, 2006, and entitled “Internet Protocol Analyzing,” the contents of which are expressly incorporated herein by reference in their entirety.

BACKGROUND

In an Internet Protocol (IP) communications network, any of a plurality of communications devices may be configured to communicate data to and from other communications devices. Users of the communications devices, network administrators, and/or third parties may desire to record these communications. Currently, networks are configured to provide a recorder to passively record such communications. While such a solution may accommodate some recording needs, many networks lack the ability to facilitate recording of communications between endpoints across a wide area network.

SUMMARY

Included are methods for facilitating routing of control data associated with a communication to a plurality of recorders. One such method, among others, includes receiving control data related to a communication and routing the received control data to at least one recorder via a layer 3 protocol.

Also included are embodiments of a Internet protocol (IP) analyzer configured to facilitate recording of at least one communication. One embodiment of an IP analyzer includes logic configured to receive control data related to a communication and logic configured to route, via a layer 2 protocol, the received control data to a recorder.

Additionally included are embodiments of a system for routing communication data to a plurality of recorders. One embodiment of a system includes an Internet Protocol (IP) analyzer coupled to a plurality of recorders, the IP analyzer configured to select at least one load balancer that is configured to receive communication data related to the communication and route control data to the selected at least one load balancer.

Other systems, methods, features, and advantages of this disclosure will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description and be within the scope of the present disclosure.

BRIEF DESCRIPTION

Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.

FIG. 1A is an exemplary network diagram illustrating a recorder passively coupled to a communications network.

FIG. 1B is an exemplary network diagram illustrating a plurality of recorders passively coupled to a subset of communications devices in the communications network from FIG. 1A.

FIG. 2 is an exemplary network diagram illustrating an embodiment of a load balancer coupled to a plurality of recorders for the network from FIG. 1A.

FIG. 3 is an exemplary network diagram illustrating use of a fail-over recorder in a network configuration, such as the configuration from FIG. 2.

FIG. 4 is an exemplary block diagram illustrating various components in an exemplary embodiment of an IP analyzer.

FIG. 5 is a flowchart illustrating exemplary steps for passively recording data from a communication in the network from FIG. 2.

FIG. 6 is a flowchart illustrating exemplary steps for passively recording data in independent streams.

FIG. 7 is a flowchart illustrating exemplary steps for providing fail-over functionality in a network, such as the network from FIG. 3.

FIG. 8 is a network diagram illustrating an exemplary configuration with an embodiment of a link protector.

FIG. 9 is a network diagram illustrating another exemplary configuration with an embodiment of a link protector coupled to an embodiment of a load balancer, such as the load balancer from FIG. 2.

FIG. 10 is a flowchart illustrating exemplary steps for protecting a link in the network from FIG. 8.

FIG. 11 is a flowchart illustrating exemplary steps for protecting a link in the network from FIG. 9.

FIG. 12 is an exemplary network configuration illustrating various components that may be used for recording a communication.

FIG. 13 is an exemplary network configuration illustrating use of an embodiment of an IP analyzer in a network configuration such as in FIG. 12.

FIG. 14 is an exemplary network configuration illustrating use an embodiment of an IP analyzer in a network configuration with multiple switches.

FIG. 15 is a sequence diagram illustrating exemplary steps that may be taken in recording a communication in the network configuration from FIG. 12.

FIG. 16 is a sequence diagram illustrating various steps that may be taken in recording a communication across a wide area network, similar to sequence diagram from FIG. 15.

FIG. 17 is a sequence diagram illustrating exemplary steps that may be taken when utilizing an IP analyzer in recording a communication in a network, such as the network configuration from FIG. 13.

FIG. 18 is a sequence diagram illustrating exemplary steps that can be taken in utilizing an embodiment of an IP analyzer when recording a communication across a gateway.

FIG. 19 is a sequence diagram illustrating exemplary steps that may be taken in utilizing an IP analyzer when recording a communication across a wide area network.

DETAILED DESCRIPTION

Included in this description are systems and methods that may be configured for recording communications utilizing call control forwarding, intelligent call control distribution, and/or other functions. In at least one nonlimiting example, a network can be configured where the point of interception of control data is remote from a desired recorder. In such a configuration, the recorder may not be supplied with mirrored control data. A component, such as an Internet Protocol (IP) analyzer may be configured to forward received control data, such as across a TCP/IP connection. Other embodiments can provide an IP analyzer that is configured to determine which recorder (or recorder group) is configured to record for a predetermined gateway or endpoint. The IP analyzer can also be configured to only forward control data to recorders that are configured to receive communication data related to a particular communication.

Load Balancer

FIG. 1A is an exemplary network diagram illustrating a recorder passively coupled to a communications network. As illustrated in the nonlimiting example of FIG. 1A, network 100, which can include a wide area network (WAN), the Internet or other network, is coupled to communications devices 102 a-102 f. Also coupled to network 100 is a recorder 104 a. As illustrated, the recorder 104 a is coupled in a passive implementation to communications devices 102. A passive implementation can include receiving mirrored data from a communication, similar to a passive tap implementation.

As a nonlimiting example, system designers can analyze network traffic through ports or Virtual Local Area Networks (VLANs) by using a System Port Analyzer (SPAN) to send a copy of the communication traffic (mirrored data) to another port on the switch that has been connected to a Remote Monitoring (RMON) probe. In operation, a copy of the data communicated between communications devices 102 may be directed to recorder 104 a. Recorder 104 a, however, is not a party to the communication and the communications devices 102 do not generally have information related to the presence and operation of recorder 104 a.

Also included in the nonlimiting example of FIG. 1A is a network pipeline 106. Network pipeline 106 is included to illustrate that while the configuration of FIG. 1A may provide recording services to a small number of communications devices, as the amount of information to be recorded increases, the network pipeline 106 may be capable of communicating more information than a single recorder can process. As such, the recorder 104 a may malfunction, burnout, or otherwise fail to provide the desired recording services.

One should note that while communications devices 102 a, 102 b, and 102 c are directly coupled together and communications devices 102 a, 102 e, and 102 f are coupled directly together, this is a nonlimiting example. As one of ordinary skill in the art will understand, any configuration for providing communications services between communications devices may be implemented. Such a configuration may also be represented with a plurality of communications devices independently coupled to the network 100, however, this too is a nonlimiting example.

FIG. 1B is an exemplary network diagram illustrating a plurality of recorders passively coupled to a subset of the communications devices from the communications network from FIG. 1A. As illustrated in the nonlimiting example of FIG. 1B, one solution for recording in a network with a large number of communications devices is to passively tap recorders to a subset of the communications devices 102 in the network 100. More specifically, as illustrated in FIG. 1B, communications devices 102 are coupled to network 100. Additionally, recorder 104 b is coupled to communications devices 102 a, 102 b, and 102 c. Similarly, recorder 104 c is coupled to communications devices 102 d, 102 e, and 102 f.

While the configuration from FIG. 1B illustrates the ability to provide recording services to all communications devices 102 in FIG. 1B, this configuration can result in problems when recording demands are not evenly distributed. As a nonlimiting example, if communications devices 102 a, 102 b, and 102 c are responsible for 80% of all recordings, then recorder 104 b is recording 80% of the network traffic. As such, recorder 104 b may reach its storage limit and/or be subject to malfunction due to the large number of recordings. Similarly, recorder 104 c will be responsible for only 20% of the recordings (in this nonlimiting example) and may be under-utilized for its capabilities.

FIG. 2 is an exemplary network diagram illustrating a load balancer coupled to a plurality of recorders for the network from FIG. 1A. More specifically, the nonlimiting example of FIG. 2 illustrates communications devices 102 coupled to network 100. Similar to the configuration from FIG. 1A, the recording traffic (at least a portion of the time) can be generally too large for any one recorder. Additionally, a network administrator may desire to control bandwidth usage by routing recording traffic to a particular recorder(s). As such, a plurality of recorders 104 d, 104 e, and 104 f may be coupled to the network 100 via a load balancer 206. Similar to the configuration from FIG. 1A, the recorders 104 d, 104 e, and 104 f are configured for passive recording of mirrored traffic. Also coupled to the load balancer is a data storage unit 208.

As a nonlimiting example, in operation, a user on communications device 102 a can initiate a communication with a user on communications device 102 d. One of the users, a system administrator, and/or a third party may desire that the communication be recorded. To facilitate the recording, data is communicated to the load balancer 206 during the communication. The load balancer 206 can be configured to receive the data for recording and route the received data to one or more of the recorders 104 d, 104 e, and 104 f. As data from different communications (and/or different streams of the same communication) is received, the load balancer 206 can determine to which recorder that data is routed. This determination can be made based on a balancing algorithm, such as a round robin algorithm, weighted round robin algorithm, a source-destination algorithm, or other algorithm, as discussed below.

Using a round robin algorithm with three recorders as illustrated in FIG. 2, the following call distribution can be achieved.

TABLE 1 Round Robin Calls Active Recorder 104d Recorder 104e Recorder 104f 0 0 0 0 Call1 Call1 0 0 Call1, Call2 Call1 Call2 0 Call1, Call3 Call1 0 Call3 Call1, Call3, Call4 Call1, Call4 0 Call3 Call3, Call4, Call5 Call4 Call5 Call3 Call3, Call4 Call4 0 Call3 Call3 0 0 Call3

As illustrated, as communications are received at the load balancer, the round robin algorithm can automatically route calls to a recorder in a manner that provides a substantially balanced workload to each recorder. More specifically, the round robin algorithm can be configured to allocate calls based on past recorder utilization. In other words, the round robin algorithm can be configured to route the most recently received call to recorders in a continuously repeating sequence. While the round robin algorithm may be desirable in certain configurations, a weighted round robin algorithm may be used to route recording traffic in other configurations.

TABLE 2 Weighted Round Robin Calls Active Recorder 104d Recorder 104e Recorder 104f 0 0 0 0 Call1 Call1 0 0 Call1, Call2 Call1 Call2 0 Call1, Call3 Call1 0 Call3 Call1, Call3, Call4 Call1 Call4 Call3 Call3, Call4, Call5 Call5 Call4 Call3 Call3, Call4 0 Call4 Call3 Call3 0 0 Call3

The call distribution in Table 2 shows that the weighted round robin algorithm considers the load on each of the recorders before routing the communication data (e.g., real time packet (RTP)) flow to the recorders. In other words, the algorithm can be configured to determine the recorder(s) that are currently utilized less than other recorders. This can result in providing a substantially balanced distribution of calls across the recorders, in that the least utilized recorder receives the call. If there are two (or more) recorders with equal current utilization, the weighted round robin algorithm can route the newly received call to the recorder next in the sequence (similar to the round robin algorithm discussed above). This means that, depending on the particular configuration, hard-disk space for storing recording data (e.g., at data storage 208) can be utilized in a roughly even manner

TABLE 3 Source-Destination Calls Active Recorder 104d Recorder 104e Recorder 104f 0 0 0 0 Call1 Call1 0 0 Call1, Call2 Call1 Call2 0 Call1, Call3 Call1 0 Call3 Call1, Call3, Call1 0 Call3 Call4 Call3, Call4, Call5 (assuming Call4 Call3 Call5 call1 finishes before call5 starts and is made between the same extension and gateway as call 1) Call3, Call4, Call5, Call6, Call7 Call4 Call3 Call5, Call6, Call7 Call3, Call4 0 Call4 Call3 Call3 0 0 Call3

While the above described round robin algorithm and weighted round robin algorithm can be utilized for many recording environments, when call data is received at the load balancer in different data streams (i.e., the communication data sent from a communications device is received in a different data stream than the communication data received at the communications device), a source-destination algorithm may be used. More specifically, if the endpoint of a VoIP call (e.g., communications device 102) receives and sends the communications data (e.g., RTP data) on different port numbers, the source-destination load balancing algorithm may be used. The source destination algorithm can more easily handle recording in such an environment, as call streams from the same communication can be sent to different recorders and provide a roughly even distribution of calls for the recorders.

FIG. 3 is an exemplary network diagram illustrating use of a fail-over recorder in a network configuration, such as the configuration from FIG. 2. More specifically, in addition to recorders 104 d, 104 e, and 104 f, the network configuration of FIG. 3 also includes a fail-over recorder 104 g. This recorder can be configured with the same functionality recorders 104 d, 104 e, and 104 f, however, this recorder may be configured for use when one or more of the recorders 104 d, 104 e, and 104 e malfunction (or otherwise are not being used). In such a scenario, the fail-over recorder 106 g can automatically begin recording in response to detecting the malfunction occurs. Additionally, if the control data is being provided to all recorders (including fail-over recorder 106 g), the transition to using the fail-over recorder 106 g can be made with minimal data loss.

Additionally, while the fail-over recorder can be kept idle when there is no recorder malfunction, this is a nonlimiting example. More specifically, other embodiments can utilize at least a portion of the fail-over recorder's functionality when the fail-over recorder 106 g is not otherwise in use. Additionally, while FIG. 3 illustrates the fail over recorder in N+1 fail-over protection (where N represents the total number of recorders, and 1 indicates the number of recorders available for fail-over), as one of ordinary skill in the art will understand, this disclosure can be interpreted to include N+M fail-over protection, where M can be any number of recorders available for fail-over. One should also note that with the above described fail-over protection employed, a network administrator may remove the malfunctioning recorder without affecting the remaining recorders 104, load balancer 206, and/or other network components.

Additionally, one should note that fail-over protection can be utilized in response to the load balancer 206 detecting a malfunction with a recorder (e.g., dead network cable). Other embodiments can include logic related to the recorder 104 for sending a signal to the load balancer 206 indicating that the recorder is to be taken out of service. Still other embodiments include logic related to the recorder 104 being configured to disable the connection with the load balancer 206 such that the load balancer 206 can detect that the link to that recorder 104 is dead.

Additional elements to the above described network configuration can include health checking logic (and/or watchdogs), where failure of one or more logic components (e.g., software) may be used to signal to the load balancer 206 to take that recorder out of service. Still other embodiments include using redundant recorders to smooth the load of data (e.g., receiving roughly equal amounts of data at each recorder) even when no recorder has failed. This can provide an increased use of available resources and ensure that all recorders are functional. In such a configuration, no one recorder is the “fail-over recorder,” as any and/or all of the recorders can provide the desired fail-over protection. This can provide more redundant capacity into the network and provide greater performance since normal operational traffic is spread evenly across the available resources.

One should also note that in at least one embodiment call data can be preserved when a call is transferred from a first recorder to a second recorder. As a nonlimiting example, recorder 104 f can be configured to record a communication between communications device 102 a and communications device 102 f. If a determination is made that it is more preferable that recorder 104 g record the communication (e.g., recorder 104 f fails, bandwidth issues with recorder 104 f, etc.) the load balancer can be configured to send subsequently received data to recorder 104 g. As one of ordinary skill in the art will understand, recorder 104 f recorded a portion of the communication and recorder 104 g recorded a portion of the communication. As such, the configuration of FIG. 3 can be configured to stitch together the two portions of the recorded communication such that, upon retrieval, the recorded data is viewed as a single recording. Additionally, depending on the particular configuration, this concept can be extended to any number of recorders.

FIG. 4 is an exemplary block diagram illustrating various components in the load balancer from FIG. 2. Generally, in terms of hardware architecture, as shown in FIG. 4, the load balancer 206 includes a processor 482, volatile and nonvolatile memory 484, data storage 495, and one or more input and/or output (I/O) device interface(s) 496 that are communicatively coupled via a local interface 492. The local interface 492 can include, for example but not limited to, one or more buses or other wired or wireless connections. The local interface 492 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface 492 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. The processor 482 may be a hardware device for executing software, particularly software stored in volatile and nonvolatile memory 484.

The processor 482 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the load balancer 206, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions. Examples of suitable commercially available microprocessors are as follows: a PA-RISC series microprocessor from Hewlett-Packard® Company, an 80×86 or Pentium® series microprocessor from Intel® Corporation, a PowerPC® microprocessor from IBM®, a Sparc® microprocessor from Sun Microsystems®, Inc, or a 68xxx series microprocessor from Motorola® Corporation.

The volatile and nonvolatile memory 484 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory 484 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the volatile and nonvolatile memory 484 can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the processor 482. Additionally volatile and nonvolatile memory 484 can also include an first routing software 486, second routing software 487 and/or third routing software 499. Additionally, the volatile and nonvolatile memory can include an operating system (not shown), depending on the particular configuration.

A nonexhaustive list of examples of suitable commercially available operating systems is as follows: (a) a Windows® operating system available from Microsoft® Corporation; (b) a Netware® operating system available from Novell®, Inc.; (c) a Macintosh® operating system available from Apple® Computer, Inc.; (d) a UNIX operating system, which is available for purchase from many vendors, such as the Hewlett-Packard® Company, Sun Microsystems®, Inc., and AT&T® Corporation; (e) a LINUX operating system, which is freeware that is readily available on the Internet 100; (f) a run time Vxworks® operating system from WindRiver® Systems, Inc.; or (g) an appliance-based operating system, such as that implemented in handheld computers or personal data assistants (PDAs) (e.g., PalmOS® available from Palm® Computing, Inc., and Windows CE® available from Microsoft® Corporation). The operating system can be configured to control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.

A system component embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the volatile and nonvolatile memory 484, so as to operate properly in connection with the Operating System.

The Input/Output devices that may be coupled to system I/O Interface(s) 496 may include input devices, for example but not limited to, network interfaces, a keyboard, mouse, scanner, microphone, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, network interfaces, a printer, display, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc. Additionally, a display interface (not shown) may facilitate connection to a display monitor or other display device.

If the load balancer 206 includes a personal computer, workstation, or the like, the software in the volatile and nonvolatile memory 484 may further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of software routines that initialize and test hardware at startup, start the Operating System, and support the transfer of data among the hardware devices. The BIOS is stored in ROM so that the BIOS can be executed when the load balancer 206 is activated.

When the load balancer 206 is in operation, the processor 482 is configured to execute software stored within the volatile and nonvolatile memory 484, to communicate data to and from the volatile and nonvolatile memory 484, and to generally control operations of the load balancer 206 pursuant to the software. Software in memory, in whole or in part, are read by the processor 482, perhaps buffered within the processor 482, and then executed.

Additionally, as stated above, while reference in FIG. 4 is made to load balancer 206, similar architecture can apply to one or more of the components in the communications network. More specifically, depending on the particular configuration, a switch, recorder, communications device, etc. may include one or more of the components illustrated in FIG. 4. Further due to the differing functionality for these devices, a variance in the hardware and/or software components may be expected.

FIG. 5 is a flowchart illustrating an embodiment of a method or exemplary steps for passively recording data from a communication in the network from FIG. 2. The first step in the nonlimiting example of FIG. 5 is to receive control data related to a communication (block 530). More specifically, referring back to FIG. 2, in at least one embodiment, when a user operating communications device 102 b establishes a communication with a user on communications device 102 e, communication data is sent between the two communications devices (and to load balancer 206). The communication data can include data related to voice, pictures, video, and/or other data for facilitating the communication. In addition to the communication data, control data may also be sent between the communication devices 102 (and load balancer 206). The control data can include data related to the dialed number, the IP address of the communications devices 102, the time of call, and/or other data.

The load balancer 206 can then receive communication data from a communication (block 532), as discussed above. Upon receiving the control data from any of a plurality of communications that may be taking place in the network, (as illustrated in block 530), the load balancer 206 can be configured to provide one or more of the recorders 104 with the control data. In at least one embodiment the load balancer 206 provides all recorders 104 d, 104 e, and 104 f with the control data (block 534). The load balancer 206 can then determine to which recorder 104 the communication data is to be routed (block 536). As discussed above, depending on the particular embodiment, any of a plurality of routing algorithms can be used, including but not limited to the round robin algorithm, the weighted round robin algorithm, and the source-destination algorithm. Once the recorder is determined, the load balancer 206 can route the communication data to the determined recorder.

FIG. 6 is a flowchart illustrating exemplary steps for passively recording data in independent streams, similar to the flowchart from FIG. 5. The first step in the nonlimiting example of FIG. 6 is for the load balancer 206 to receive control data related to a communication (block 630). Next, the load balancer 206 can receive a first stream of communication data (block 634). The load balancer 206 can then receive a second stream of communication data (block 636). As discussed above, depending on the particular configuration, the communication can be received by the load balancer 206 via one stream, or by more than one stream. In this particular nonlimiting example, the communication data is received in a plurality of different streams.

The load balancer 206 can then provide the recorders with the received control data (block 638). The load balancer 206 can then determine to which recorder the first communication stream data is to be routed (block 640) and determine to which recorder the second communication stream is to be routed (block 642). The load balancer 206 can then route the first communication stream to the first determined recorder (block 644) and route the second communication stream to the second determined recorder (block 646).

FIG. 7 is a flowchart illustrating exemplary steps for providing fail-over functionality in a network, such as the network from FIG. 3. The first step in the nonlimiting example of FIG. 7 is for the load balancer 206 to receive data related to a communication (block 730). As discussed above, the data can include control data, as well as communication data. Once the data is received, the load balancer can send the received control data to all recorders 104 coupled to the load balancer 206 (block 732). The load balancer 206 can then determine to which recorder to send the received communication data (block 734) and then send communication data to a recorder (block 736). The load balancer 206 can then detect a malfunction with the recorder (block 738). The load balancer 206 can make this determination in any of a plurality of ways including the load balancer 206 detecting a malfunction with a recorder (e.g., dead network cable). Other embodiments can provide that logic related to the recorder 104 sends a signal to the load balancer 206 indicating that the recorder is to be taken out of service. Still other embodiments provide that logic related to the recorder 104 disables the connection with the load balancer 206 such that the load balancer 206 can detect that the link to that recorder 104 is dead. Regardless of the technique for detecting the malfunction, the recorder can then begin routing the communication data to the fail-over recorder (block 740).

One should also note, that while the load balancer can be configured to detect errors in recorders, at least one embodiment can include a recorder with logic to self detect errors with the recorder. As a nonlimiting example, a recorder can be configured with logic for monitoring various hardware and/or software components using Intelligent Platform Management Interface (IPMI) and/or other protocol.

Link Protector

FIG. 8 is a network diagram illustrating an exemplary configuration with a link protector. Similar to the configuration from FIG. 2, the configuration of FIG. 8 includes a plurality of communications devices 102 coupled to network 100. In such a configuration, a user on communications device 102 a can initiate a communication with a user on communications device 102 f. Once the communication session commences (or anytime thereafter), mirrored data can be sent for recording. As discussed above with respect to FIGS. 1A and 1B, a recorder can be passively coupled to the communications network 100 to facilitate this recording. While coupling a recorder to the network as depicted in FIGS. 1A and 1B may provide the desired recording services, a problem can result if one of the recorders fails or otherwise malfunctions. In such a scenario, data can be lost until the malfunction is addressed.

The configuration from FIG. 8, however, illustrates an embodiment of a network for addressing hardware malfunction in such a scenario. More specifically, by passively coupling a link protector 810 a to the network 100, mirrored data can be received by the link protector 810 a. The link protector 810 a can route the received data to the primary recorder (in this nonlimiting example, recorder 104f). If a hardware malfunction occurs (such as a severance of the link between recorder 104 f and link protector 810 a), the link protector can automatically route subsequently received data to the secondary recorder 104 g. By routing subsequently received data to the secondary recorder 104 g, recording can continue with minimal data loss.

FIG. 9 is a network diagram illustrating another exemplary configuration with a link protector coupled to a load balancer, such as the load balancer from FIG. 2. Similar to the configuration from FIG. 8, a plurality of communications devices 102 is coupled to communications network 100. Also coupled to communications network 100 are switches 912 a and 912 b, which can provide connection services between communications devices 102. Switch 912 a is coupled to link protector 810 b and link protector 810 c. Link protector 810 b is coupled to load balancer 206 b, as well as load balancer 206 c. Similarly, link protector 810 c is coupled to load balancer 206 b and load balancer 206 c. In at least one configuration, link protector 810 b can be configured to receive communication data related to the current communication, while link protector 810 c is configured to receive control data. As discussed above, communication data can include voice, video, picture, and/or other data that facilitates the communication between communications devices 102. Control data can include other data for indicating various attributes of the communication, such as data related to the dialed number, the IP address of the communications devices 102, the time of call, and/or other data. Link protectors 810 d and 810 e are each coupled to load balancer 206 b and load balancer 206 c and may have similar functionality to link protectors 810 b and 810 c. Load balancers 206 b and 206 c are coupled to recorders 104 h, 104 i and 104 j.

In operation, a call is initiated between communications device 102 c and communications device 102 d. This communication can be facilitated by switch 912 a (depending on the particular configuration 912 may also facilitate the communication). Link protector 810 b receives communication data and sends the received communication data to load balancer 206 b (which is the primary load balancer for switch 912 a). Similarly, link protector 810 c receives control data and sends this data to load balancer 206 b.

With respect to the configuration of FIG. 9, if the link between link protector 810 b and load balancer 206 b is severed, link protector 810 b can automatically begin sending subsequently received communications data to load balancer 206 c. Similarly, if the link between 810 e and load balancer 206 c is severed, the link protector 810 e can route subsequently received control data to load balancer 206 b (which is the secondary load balancer for switch 912 b), if this data is not already being sent to load balancer 206 b. Similar routing can occur with link protectors 810 c and 810 d.

Regardless of the status of links between load balancers 206 and link protectors 810, the load balancers 206 can receive data from the link protectors 810 and distribute this data to recorders 104 according to any of a plurality of algorithms, as indicated above. Also as indicated above, a data storage unit (not shown) can be coupled to recorders 104.

In addition to detecting a hardware malfunction (such as a severed link), link protectors 810 can be configured to “heartbeat” those components coupled to link protectors 810. More specifically, link protector 810 b can be configured with logic for determining whether load balancers 206, as well as recorders 104 are functioning. As a nonlimiting example, link protector 810 b can be configured to routinely and/or continuously send a status request signal (“heartbeat”) to load balancers 206 b and 206 c. The status request signal can be configured to determine whether the logic in the load balancers 206 is operating properly. Upon receiving an indication of the status of load balancers 206, the link protector 810 b can determine whether the load balancers 206 are operating as desired. Similarly, functionality data related to recorders 104 can be determined in a similar fashion. If the link protector determines that a load balancer 206 and/or a recorder 104 are not operating properly, the link protector can route subsequently received data to those components that are operating properly. More specifically, in at least one embodiment, the link protector can be configured to identify a hardware, software, and/or communications issue with a recorder and/or load balancer. As a nonlimiting example, the link protector can be configured with logic, such as (but not limited to) IPMI for determining various issues.

FIG. 10 is a flowchart illustrating exemplary steps for protecting a link in the network from FIG. 8. The first step in the nonlimiting example of FIG. 10 is for the link protector 810 to receive communication data from a switch (block 1030). As discussed above, the switch (not shown in FIG. 8) can be configured to send both control data and communication data related to a communication. Once the data is received, the link protector 810 a can determine whether the first recorder 104 f is operational (block 1032). If the first recorder 104 f is operational, the link protector 810 a can send at least a portion of the received data to the recorder 104 f (block 1034). If the link detector 810 a determines that the first recorder 104 f is not operational, the link detector 810 a can send at least a portion of the received data to the second recorder 104 g (block 1036). The link detector 810 a can then determine whether there is more data to receive (block 1038). If the link detector 810 a determines that there is more data to receive, the flowchart returns to block 1030 and the process begins again.

While the flowchart with respect to FIG. 10 illustrates a configuration where the link detector 810 a determines whether the first recorder 104 f is operational each time data is received, this is a nonlimiting example. More specifically, in at least one embodiment, if the link protector 810 a determines that the first recorder 104 f is not operational, the link detector 810 a automatically routes subsequently received data to the second recorder 104 g without making any determinations. This can continue until the malfunctioning recorder 104 f is repaired and/or replaced and the link protector 810 a is reset.

FIG. 11 is a flowchart illustrating exemplary steps for protecting a link in the network from FIG. 9. The first step in the nonlimiting example of FIG. 11 is for the link protector 810 to receive data from a switch 912 (block 1130). Upon receiving the data, the link protector can determine whether the first load balancer is operating properly (block 1132). More specifically, depending on the particular configuration, the link protector can determine whether the load balancer has encountered a hardware error, a software error, a communications error, and/or any other issue that could effect recording. If the link protector determines that the first load balancer is operating properly, the link protector can send data to the first load balancer (block 1134). If, on the other hand, the link protector determines that the first load balancer is not operating properly, the link protector can send data related to the malfunction, which can include a signal or alarm (block 1136). The link protector can then determine whether a second load balancer is operating properly (block 1138). If the second load balancer is operating properly, the link protector can send data to the second load balancer (block 1140). If, on the other hand, the link protector determines that the second load balancer is not operating properly, the link protector can send data related to a malfunction (block 1142).

As illustrated in FIG. 11, block 1142 does not flow to an end block. Such a configuration is intended to represent the possibility that the link protector can be configured to provide link protection with any number of load balancers and/or recorders. As one of ordinary skill in the art will understand, blocks similar to blocks 1136, 1138, 1140, and 1142 can be utilized for additional load balancers.

IP Analyzer

FIG. 12 is an exemplary network configuration illustrating various components that may be used for recording a communication. As illustrated, communications network 100 (which can include a WAN, Asynchronous Transfer Mode (ATM) network, the Internet and/or other network) is coupled to gateway 1216 y and 1216 z. Gateway 1216 y is coupled to switch 912 y. Similarly, gateway 1216 z is coupled to switch 912 z. Call control engine 1218 y is coupled to switch 912 y as well as communications devices 102 w and 102 x. Call control engine 1218 z is coupled to switch 912 z and communications devices 102 y and 102 z. Load balancer 206 y is passively coupled to the link between gateway 1216 y and switch 912 y. Load balancer 206 z is passively coupled between gateway 1216 z and switch 912 z. Load balancer 206 y is also coupled to a recorder bank that includes recorders 104 u, 104 v, and 104 w. Load balancer 206 z is coupled to a recorder bank that includes recorders 104 x, 104 y, and 104 z. Additionally, load balancer 206 y is passively coupled to call control engine 1218 y and load balancer 206 z is passively coupled to call control engine 1218 z. similarly,

In operation, if a caller initiates a communication from communications device 102 w to communications device 102 s (which is external to the network of FIG. 12 and may be coupled to gateway 1216 y via a Public Switched Telephone Network (PSTN), the Internet, and/or other network), gateway 1216 y can facilitate the communication. As data is communicated between the communications devices 102 w and 102 s, load balancer 206 y receives mirrored communication data sent between gateway 1216 y and switch 912 y. As discussed above, load balancer 206 y can be configured to send the received communication data to one or more of the recorders 104 u, 104 v, and 104 w. Similarly, call control engine 1218 y receives control data related to the communication. Load balancer 206 y receives mirrored control data from the call control engine 1218 y. Load balancer 206 y can then provide the received control data to one or more recorders 104 u, 104 v, and 104 w.

While such a configuration may enable recording of communications between two communications devices being serviced by the same gateway, problems may occur for recording across a plurality of gateways. More specifically, if a user on communications device 102 w desires to communicate with a user on communications device 102 t (which is external to the network of FIG. 12 and may be coupled to gateway 1216 z via a PSTN, the Internet, and/or to the network), recording may be a difficult task. As a nonlimiting example, by initiating a communication from communications device 102 w, the data is communicated via network 100 to gateway 1216 z. Gateway 1216 z sends the received data to communications device 102 t.

However, in recording the communication, load balancer 206 z receives mirrored data sent from gateway 1216 z. A problem can occur in sending the control data to the load balancer 206 z, in that the call control engine 1218 z (from which the load balancer 206 z generally receives mirrored control data) may not receive the control data (due, at least in part, by a lack of layer 2 connectivity between gateways). As data ports for mirrored data from switch 912 z (and 912 y) may be limited, recording difficulties may result.

FIG. 13 is an exemplary network configuration illustrating use of an IP analyzer in a network configuration such as in FIG. 12. As illustrated, the network of FIG. 12 is illustrated with the addition of IP analyzers 1218 y and 1218 z coupled to call control engines 1322 y and 1322 z, respectively. As illustrated, IP analyzer 1320 can include one or more components (e.g., software servers and hardware servers), depending on the particular configuration. Additionally, IP analyzers 1322 y and 1322 z can be configured as servers that include logic configured to facilitate recording across a plurality of gateways.

More specifically, in at least one nonlimiting example, if a user on communications device 102 w desires to initiate a communication with a user on communications device 102 t, control data associated with the communication can be sent to IP analyzer 1320 y. The IP analyzer 1320 y can be configured to send the received control data to load balancer 206 z. Additionally, as discussed above, the mirrored communications data can be sent to load balancer 206 z. With both the control data and the communication data, the load balancer can facilitate recording of the communication via one or more of the recorders 104 x, 104 y, and 104 z.

One should note that depending on the particular embodiment, the IP analyzer 1320 can be configured for call control forwarding and/or intelligent call control distribution. More specifically, with respect to call control forwarding, the recorders 104 x, 104 y, and 104 z are generally unable to receive mirrored data from call control engine 1218 y due to the lack of layer 2 network connectivity between the two components. The IP analyzer 1320 y can be configured to receive mirrored control data from call control engine 1218 y. The IP analyzer 1320 y can receive and forward control data to one or more of the recorders 104 x, 104 y, and 104 z across a TCP/IP connection or other medium. Additionally, the IP analyzer 1320 y can also be configured to send the control data to recorders 104 u, 104 v, and 104 w with little or no concept of the geographic location of the recorders. During call control forwarding, the IP analyzer can be configured to forward all control data to all recorders communicatively coupled to the IP analyzer 1320 y.

With respect to intelligent call control distribution, the IP analyzer 1320 y can be configured to intelligently distribute control data to recorders based on a predetermined address for each recorder (or recorder bank). More specifically, if a communication commences between communications device 102 w and 102 s, load balancer 206 z (and thus recorders 104 x, 104 y, and 104 z) will generally not receive communication data related to this communication. As such, with intelligent call control distribution, IP analyzer 1320 y can be configured to send control data only to the load balancer that facilitates recording of the call (in this nonlimiting example load balancer 206 y), which has a known address (e.g., IP address and Media Access Control (MAC) address). Other load balancers (and thus recorders) that are not configured to receive communication data related to this particular communication will not receive control data related to the communication.

Additionally, while one IP analyzer 1320 can be utilized for predetermined network traffic, in at least one configuration, a plurality of IP analyzers can be utilized for fail-over protection. Additionally, depending on the particular configuration, one or more link protectors and/or load balancers may be coupled to the IP analyzer 1320.

FIG. 14 is an exemplary network configuration illustrating use an embodiment of an IP analyzer in a network configuration with multiple switches. As illustrated, the network 100 is coupled to a gateway 1216 k, which is also coupled to switches 912 k and 912 m. Switch 912 k is coupled to call control engine 1218 k, which is coupled to communications devices 102 k and 102l, as well as IP analyzer 1320 k. Load balancer 206 k is passively coupled between gateway 1216 k and switch 912 k. Load balancer 206 k is also coupled to recorders 104 k, 1041, and 104 m.

Similarly, load balancer 206 m is passively coupled between gateway 1216 k and switch 912 m. Load balancer is also coupled to recorders 104 n, 104 o, and 104 p. Switch 912 m is coupled to call control engine 1218 m. Call control engine 1218 m is coupled to communications devices 102 m and 102 n, as well as IP analyzer 1320 m.

FIG. 15 is a sequence diagram illustrating exemplary steps that may be taken in recording a communication in the network configuration from FIG. 12. More specifically, as discussed above, in attempting to record a communication across a single gateway without use of an IP analyzer 1322, the first step for facilitating the communication may include communications device 1 (component 102 w) sending data to the gateway 1216 (step 1530). The gateway 1216 y then sends at least a portion of the data to switch 2 (not shown), as illustrated in step 1534. Switch 2 (not shown) can then send at least a portion of the received data to communications device 2 (not shown), as illustrated in step 1536.

Additionally, in attempting to record the communication data related to the communication, the first step is for communications device 1 (component 102 w) to send data to switch 1 (component 912 y), as illustrated in step 1538. Switch 1 (component 912 y) then sends the received communication data to recording cluster 1 (component 206 y).

Similarly, in attempting to record control data in this nonlimiting example, communications device 1 (component 102 w) sends control data to call control engine 1 (component 1218 y), as illustrated in step 1542. Call control engine 1 (component 1218 y) then sends at least a portion of the received control data to recording cluster 1 (component 206 y), as illustrated in step 1546.

FIG. 16 is a sequence diagram illustrating various steps that may be taken in recording a communication across a wide area network, similar to sequence diagram from FIG. 15. As illustrated in this nonlimiting example, in facilitating the communication, communications device 1 (component 102 w) sends data to WAN (component 100), as illustrated in step 1630. WAN (component 100) sends the received data to gateway 2 (component 1216 z), as illustrated in step 1632. Gateway 2 (component 1216 z) sends at least a portion of the data to switch 2 (component 912 z), as illustrated in step 1634. Switch 2 (component 912 z) sends at least a portion of the received data to communications device 2 (component 102 z).

With respect to the communication data for recording, communications device 1 (component 102 w) sends communications data to WAN (component 100), as illustrated in step 1638. WAN (component 100) sends at least a portion of the received data to gateway 2 (component 1218 z), as illustrated in step 1640. Gateway 2 (component 1218 z) sends at least a portion of that data to recording cluster 2 (component 206 z), as illustrated in step 1642.

With respect to the control data for recording, communications device 1 (component 102 w) sends the control data to call control engine 1 (component 1218 y), as illustrated in step 1644. Call control engine sends at least a portion of the received control data to recording cluster 1 (component 206 y), as illustrated in step 1646. As demonstrated in this nonlimiting example, the control data is received at recording cluster 1 (component 206 y), while the communication data is received at recording cluster 2 (component 206 z). For at least the reason, that in some configurations, layer 2 connectivity may not exist between gateways, recording of communications that traverse a plurality of gateways without an IP analyzer may be difficult.

FIG. 17 is a sequence diagram illustrating exemplary steps that may be taken when utilizing an IP analyzer in recording a communication in a network, such as the network configuration from FIG. 13. In this nonlimiting example, in facilitating a communication between communications device 1 (component 102 w) and communications device 2 (component 102 x), communications device 1 (component 102 w) sends data to switch (component 912 y), as illustrated in step 1730. Switch (component 912 y) sends at least a portion of the received data to communications device (component 102 x), as illustrated in 1732.

To record communications data in this nonlimiting example, communications device 1 (component 102 w) sends communications data to switch (component 912 y), as illustrated in step 1734. Switch (component 912 y) then sends at least a portion of the received data to recording cluster (component 206 y), as illustrated in step 1736.

To record control data, communications device 1 (component 102 w) sends at least a portion of the control data for the communication to call control engine (component 1218 y), as illustrated in step 1738. Call control engine (component 1218 y) sends at least a portion of the received data to IP analyzer (component 1320 y), as illustrated in step 1740. IP analyzer (component 1320 y) then sends at least a portion of the control data to the recording cluster (component 206 y), as illustrated in step 1742. As discussed above, by utilizing an IP analyzer, both the control data and the communications data can be sent to the desired load balancer for recording.

FIG. 18 is a sequence diagram illustrating exemplary steps that can be taken in utilizing an embodiment of an IP analyzer when recording a communication across a gateway. The first step for facilitating a communication between communications device 1 (component 102 k) and communications device 2 (102 n) is for communications device 1 (component 102 k) to send data to gateway (component 1216 k), as illustrated in step 1830. Gateway (component 1216 k) then sends the received data to switch 2 (component 912 m), as illustrated in step 1834. Switch 2 (912 m) then sends the received data to communications device 2 (102 n), as illustrated in step 1836.

In sending communications data for recording, communications device 1 (component 102 k) sends data to gateway (component 1216 k), as illustrated in step 1836. Gateway (component 1216 k) then sends the received data to switch 912 m), as illustrated in step 1840. Recording cluster 2 (206 m) then receives mirrored data from switch 2 (912 m), as illustrated in step 1842.

In communicating control data for recording, communications device 1 (component 102 k) sends control data to call control engine 1 (component 1218 k), as illustrated in step 1844. Call control engine 1 (component 1218 k) then sends data to IP analyzer 1 (component 1320 k), as illustrated in step 1846. IP analyzer (component 1320 k) then sends at least a portion of the received control data to load balancer 206 m), as illustrated in step 1848.

Similar to the discussion above, the IP analyzer in this nonlimiting example enables a desired load balancer 206 m to receive both control data and communications data related to the call. The load balancer 206 m can be configured to then send the received data to one or more of the recorders 104 n, 104 o, and/or 104 p coupled to the load balancer 206 m.

FIG. 19 is a sequence diagram illustrating exemplary steps that may be taken in utilizing an IP analyzer when recording a communication across a wide area network. The first step in facilitating a communication between communications device 1 (component 102 w) and communications device 2 (component 102 y) is for communications device 1 (component 102 w) to send data to WAN (component 100), as illustrated in block 1930.

In sending communication data for recording communications device 1 (component 102 w) sends communication data to WAN (component 100), as illustrated in step 1938. WAN (component 100), then sends the received data to gateway 2 (component 1216 z), as illustrated in step 1940. Recording cluster 2 (component 206 z) then receives mirrored data from gateway 2 (component 1216 z), as illustrated in step 1942.

In sending control data for recording, communications device 1 (component 102 w) sends control data to call control engine 1 (component 1218 y), as illustrated in step 1944. Call control engine 1 (component 1218 y) then sends the received data to IP analyzer 1 (component 1320 y), as illustrated in step 1946. IP analyzer 1 (component 1320 y) then sends at least a portion of the received data to recording cluster 2 (component 206 z) for recording, as illustrated in 1948. As discussed above, the nonlimiting example of FIG. 19 illustrates that in utilizing an IP analyzer for recording across a network, such as a WAN, ATM, the Internet, etc., both the communication data and the control data can be sent to a desired load balancer and/or recorder.

One should also note that depending on the particular configuration the IP analyzer can be configured to receive control data interpret the received control data. Additionally, depending on the particular embodiment, the IP analyzer can issue a start record command, a stop record command, and/or other commands one or more recorders.

As one of ordinary skill in the art will understand, while the flowcharts and sequence diagrams discussed in this disclosure are illustrated as occurring in a particular order, this is a nonlimiting example. The steps in this disclosure can occur in any of a plurality of different orders, and may include more or fewer steps than illustrated herein. Additionally, while the steps in FIGS. 4 and 5 relate to steps that are performed by load balancer 206 and the steps in FIGS. 10 and 11 are performed by a link protector, these are also a nonlimiting examples. As one of ordinary skill in the art will understand, depending on the particular configuration, one or more of the steps can be performed by a different component than described in those examples.

One should note that the flowcharts and sequence diagrams included herein show the architecture, functionality, and/or operation of a possible implementation of logic. In this regard, each block can be interpreted to represent a hardware component, a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

One should also note that any of the programs listed herein, which can include an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.

It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiments without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure. 

1. Internet protocol (IP) analyzer configured to facilitate recording of at least one communication, the IP analyzer comprising: a processor; and a volatile and nonvolatile memory, in which the processor executes: logic configured to receive control data related to a communication at a first site; logic configured to select at least one recorder at a second site that is configured to receive communication data related to the communication at the first site, wherein communication data related to the communication is sent to the selected at least one recorder at the second site; and logic configured to route the received control data to the selected at least one recorder at the second site, the at least one recorder at the second site receiving the control data related to the communication at the first site, wherein the first site and the second site are disparate locations each having a gateway that connects to a through a network.
 2. The IP analyzer of claim 1, wherein the communication traverses at least one of the following: a wide area network (WAN) and an Asynchronous Transfer Mode (ATM) network.
 3. The IP analyzer of claim 1, wherein the logic configured to receive the control data is further configured to passively receive mirrored control data.
 4. The IP analyzer of claim 3, further comprising logic configured to passively receive the mirrored control data from the call control engine.
 5. The IP analyzer of claim 1, further comprising logic configured to send control data to all recorders communicatively coupled to the IP analyzer.
 6. The IP analyzer of claim 1, further comprising logic configured to determine an address associated with the at least one recorder that is configured to receive the communication data.
 7. The IP analyzer of claim 1, further comprising logic configured to send data to a load balancer via a TCP/IP connection.
 8. A method for facilitating routing of control data associated with a communication to a plurality of recorders, the method comprising: receiving control data related to a communication at an Internet Protocol (IP) analyzer at a first site, wherein the communication is configured for transmission across a Wide Area Network (WAN); and routing the received control data by the IP analyzer to at least one recorder at a second site, wherein the first site and the second site are disparate locations each having a gateway that connects to a through the WAN.
 9. The method of claim 8, wherein routing the received control data to at least one recorder includes routing the received control data to at least one load balancer, the at least one load balancer being configured to distribute received data among a plurality of recorders.
 10. The method of claim 8, further comprising selecting at least one load balancer for receiving communication data related to the communication.
 11. The method of claim 8, further comprising routing the received control data to all recorders that are communicatively coupled to the WAN.
 12. The method of claim 8, wherein sending control data to at least one recorder includes sending control data across a TCP/IP connection.
 13. The method of claim 12, wherein the received control data includes passively received mirrored data.
 14. The method of claim 8, wherein the received control data is received from a call control engine.
 15. A system for routing communication data to a plurality of recorders, comprising: at least one recorder at a first site configured to receive communications data from a second site and interpret at least a portion of the communications data; and an Internet Protocol (IP) analyzer coupled to the at least one recorder at the first site, the IP analyzer configured to: receive control data related to the communication from the second site; select the at least one recorder at the first that is configured to receive communication data related to the communication from the second site; and route control data from the second site to the selected at least one recorder at the first site.
 16. The system of claim 15, wherein the communication traverses at least one of the following: a wide area network (WAN) and an Asynchronous Transfer Mode (ATM) network.
 17. The system of claim 15, wherein the IP analyzer is further configured to passively receive mirrored control data.
 18. The system of claim 17, wherein the IP analyzer is configured to passively receive the mirrored control data from the call control engine.
 19. The system of claim 15, further comprising a plurality of recorders, at least one of the plurality of recorders being configured to receive data related to the communication.
 20. The system of claim 15, wherein the IP analyzer is further configured to interpret the received data and issue at least one record command to at least one recorder. 